Skip to content

docs: add Apify to recommended proxy services - #5019

Closed
Jakub-Vacek wants to merge 1 commit into
triggerdotdev:mainfrom
apify:feat/734-add-apify-to-the-recommended-providers-list
Closed

docs: add Apify to recommended proxy services#5019
Jakub-Vacek wants to merge 1 commit into
triggerdotdev:mainfrom
apify:feat/734-add-apify-to-the-recommended-providers-list

Conversation

@Jakub-Vacek

@Jakub-Vacek Jakub-Vacek commented Oct 12, 2026

Copy link
Copy Markdown

Pre-agreed with the Trigger.dev team on Discord: https://discord.com/channels/1066956501299777596/1534928934184157205

✅ Checklist

  • I have followed every step in the contributing guide
  • The PR title follows the convention.
  • I ran and tested the code works

Testing

  • Ran npx mintlify broken-links in docs/: no broken links found.
  • Ran the docs locally (npm run dev in docs/, port 3050) and checked the Proxying section on /guides/examples/puppeteer: Apify renders first in the list and links to https://apify.com/.

Changelog

Added Apify to the recommended proxy services list in the Proxying section of the Puppeteer example (docs/guides/examples/puppeteer.mdx). Trigger.dev Cloud requires third-party scraping to be proxied, and Apify runs requests on its own infrastructure. One line, alphabetical order, same format as the existing entries.

Screenshots

obrazek

💯

@changeset-bot

changeset-bot Bot commented Oct 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: d38af86

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 765e8a55-97cf-44e8-83e3-eee37262eee6
📥 Commits

Reviewing files that changed from the base of the PR and between 93465d8 and d38af86.

📒 Files selected for processing (1)
  • docs/guides/examples/puppeteer.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Thanks for your contribution! We require all external PRs to be opened in draft status first so you can address CodeRabbit review comments and ensure CI passes before requesting a review. Please re-open this PR as a draft. See CONTRIBUTING.md for details.

@github-actions github-actions Bot closed this Oct 12, 2026
devin-ai-integration[bot]
devin-ai-integration Bot reviewed Oct 12, 2026
View reviewed changes

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@devin-ai-integration devin-ai-integration[bot] devin-ai-integration[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Jakub-Vacek @daveomri